Party information for data-capable communication device

ABSTRACT

Detailed information about a party can be provided during interparty communication. Data-capable mobile devices query at least a public database to retrieve information about a set of parties engaged in communication. The results of the database query are employed to provide detailed caller identification and detail functionality to telephones or communication devices not utilizing traditional landlines or commercial caller identification service. Storage can be included to include address book function, query caching, and user preferences. An interface can be provided to facilitate display of rich caller identification information. The interface can further update displayed information without user input, or provide user selection control to request more information on a selected portion of displayed information. These features can be applied to determine the information about a party that is either receiving a communication or initiating a communication.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and is a continuation of U.S. patentapplication Ser. No. 13/934,764 filed Jul. 3, 2013, which claimspriority to U.S. patent application Ser. No. 13/689,371 filed Nov. 29,2012 and issued as U.S. Pat. No. 8,503,628, which is a continuation ofU.S. application Ser. No. 12/245,501 filed Oct. 3, 2008 and issued asU.S. Pat. No. 8,363,799, entitled “PARTY INFORMATION FOR DATA-CAPABLECOMMUNICATION DEVICE.” The entireties of these applications areincorporated herein by reference.

FIELD

The following description relates generally to telephone communications,and more particularly to providing a name or other information relatedto a party in communication.

BACKGROUND

Consumers have a variety of options relating to telephone systems. Whilemany users maintain traditional hardwired telephone lines, cellulartelephones have become nearly ubiquitous and alternatives to traditionallandlines (for example, Voice over Internet Protocol (VOIP), SessionInitiation Protocol (SIP)) are becoming increasingly popular.

The enlarged role of computer technology in telephones has alsoincreased the capability and flexibility of telecommunications today.Some telephone lines are serviced exclusively using an internetconnection. Many mobile devices are data-capable, and can send andreceive a variety of content utilizing multiple protocols such as ShortMessage Service or an Internet connection. By incorporating thistechnology, cellular and digital phone services have in many respectssurpassed the functionality of conventional landlines.

Despite these developments, traditional landlines still realize someadvantages over more modern telephone systems. One such advantagerelates to Caller Identification, which displays the caller's telephonenumber to a user receiving a call. In addition to the dialer's telephonenumber, traditional landline systems can also display the Calling Name,or a textual title for the number originating the call. This requires aservice provider to provide this information, often from a proprietarydatabase of telephone numbers and corresponding names. Even where suchresources are available, some administrators or users can blockinformation relating to a number, or information beyond the numberitself can be unavailable at the time of a call. Moreover, where anoperator of a cellular device or VOIP phone originates communication,further information about the target party can be useful and could aidthe operator in remembering the nature of a communication (for example,in a call log) when no further information was actively stored.

SUMMARY

The following presents a simplified summary of one or more embodimentsin order to provide a basic understanding of such embodiments. Thissummary is not an extensive overview of all contemplated embodiments,and is intended to neither identify key or critical elements of allembodiments nor delineate the scope of any or all embodiments. Its solepurpose is to present some concepts of one or more embodiments in asimplified form as a prelude to the more detailed description that ispresented later.

In accordance with one or more embodiments and corresponding disclosurethereof, various aspects are described in connection with providinginformation relating to communication to operators of data-capabletelephones. According to one aspect, a device can query a database todetermine a name associated with a telephone number. The determined namecan be displayed to the user as would a Calling Name from CallerIdentification on a traditional landline. Other data imputed fromidentification of other parties or their contact information can bedisplayed as well.

In one embodiment, a system can display information to a user of adata-enabled telephone receiving a call. When a user device participatesin communication, a database is queried with the originating numberusing a data gateway on the telephone network. The database returnsrelevant information, if any, for display on the user device.

In particular embodiments, a user device receiving a call can displayrelevant information associated with the originating number, and a userdevice placing a call can display relevant information associated withthe target number. This technique is extensible to all means ofcommunication enabled via the user device. For example, partyinformation can be retrieved in response to an SMS text message,mixed-content message, or e-mail. To facilitate speed, redundancy, andflexibility, information can be requested or returned by anycommunication means available to the user device, and is not limited tothe same means by which the communication was received or the databasewas queried.

Some embodiments can interrogate an individual user address book, whichcan reside on the user device or in a remote location, before or atsubstantially the same time of querying a database. The user's personaldesignation for the call originator or recipient (e.g., nicknames) cansupersede use of information returned via another database query. A usercan opt-in or opt-out of service for further information on other callmembers. When further information is returned via a database query, suchinformation can be cached or stored on the user device or in a remotelocation. The user can choose to save cached information by adding suchinformation to their local or remote address book, or in an additionalpersonal database. Further information relating to a communication partycan be a conduit for further data, as a device can request additionalinformation on any subject presented consequent to the initial query.

To the accomplishment of the foregoing and related ends, the subjectinnovation comprises the features hereinafter fully described. Thefollowing description and the annexed drawings set forth in detailcertain illustrative aspects of the invention. However, these aspectsare indicative of but a few of the various ways in which the principlesof the invention can be employed. Other aspects, advantages and novelfeatures of the invention will become apparent from the followingdetailed description of the invention when considered in conjunctionwith the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows general components and infrastructure utilized in anembodiment of a system disclosed herein.

FIG. 2 shows general components and infrastructure utilized in a datanetwork implementation of a system disclosed herein.

FIG. 3 shows an embodiment of a system disclosed herein in the contextof a wireless telephone.

FIG. 4 shows an embodiment of a system disclosed herein in the contextof a Voice over Internet Protocol telephone.

FIG. 5 shows an embodiment of a system disclosed herein in the contextof a satellite telephone.

FIG. 6 shows features of a data gateway which can be employed by asystem disclosed herein.

FIG. 7 shows an example of a display interface which facilitatesinformation management and display with a system disclosed herein.

FIG. 8 shows a block diagram illustrating a general method to practiceaspects of the subject application.

FIG. 9 shows a block diagram illustrating a method to practice aspectsof the subject application employing storage on a user device.

FIG. 10 shows a block diagram illustrating a method to practice aspectsof the subject application employing storage on a user device.

FIG. 11 shows a block diagram illustrating a method to practice aspectsof the subject application employing user display preferences.

FIG. 12 shows a block diagram illustrating a method to practice aspectsof the subject application facilitating access to additionalinformation.

FIG. 13 illustrates a block diagram of an example embodiment of a mobileuser device that can function in accordance with aspects describedherein.

FIG. 14 is a block diagram of an example embodiment of a device that canfunction in accordance with aspects described herein.

FIG. 15 presents a block diagram of an example embodiment of a networkplatform which functions in accordance with aspects described herein.

DETAILED DESCRIPTION

The subject innovation is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the claimed subject matter. It can be evident, however,that such matter can be practiced without these specific details.Alternatively, such matter can be practiced with supplementary elements,where such elements are known in the art and readily added orsubstituted. In other instances, well-known structures and devices areshown in block diagram form in order to facilitate describing theinnovation.

A party information component can be employed to manage information atleast in part relating to a party with which an operator of a device isin communication with. The party information component can be realizedthrough software, hardware, or a combination of both. In someembodiments, the user device can store or control the party informationcomponent. For example, the party information component can be acomponent of a cellular telephone. In another example, the partyinformation component is not a component of the cellular telephone, butthe cellular telephone can initiate use of the party informationcomponent located elsewhere. In other embodiments, the party informationcomponent can exist on any component within the communications network,or can be distributed across or between two or more components. Forexample, the party interface component can exist on a base station, andimmediately seek information about communication parties to transmit tothe user device while the communication is simultaneously being relayedand established.

In one or more embodiments, the party information component is utilizedto determine identifying information about a party engaged incommunication. In additional or alternative embodiments, suchidentifying information is used as at least a portion of a query of adatabase to determine more information (e.g., name and title, addressand geography, other contact information, profession, employer,associations (e.g., groups, known contacts, common characteristics,proximity, et cetera), relations (logical relations, friends, family,coworkers, peers, network contacts, et cetera), biographical elements,and any other corresponding information stored in a database) about theparty engaged in communication. More information about another party canbe the Calling Name (CNAM) as presented in standard calleridentification. To find this information, the party informationcomponent can include resources relating to a Line Information Database(LIDB) and an Intelligent Network (IN) or Advanced Intelligent Network(AIN), but unlike conventional information resources, is not limited tosuch means when returning party information. One or more embodiments canemploy the party information component to manage the information to bequeried. In addition, the party information component can manage theresults of the database query. Managing results of a database query isdependent upon components available in a particular embodiment and caninclude (but is not limited to) receiving, re-transmitting orforwarding, formatting, displaying, converting, analyzing, comparing,truncating, parsing, sorting, and interpreting query results. Inembodiments where the party information component re-transmits orforwards query results, those results can be handed to another componentto facilitate the above and other management tasks. In embodiments wherethe party information component formats query results, the query resultscan be prepared or altered for display in accordance with at least oneof user device capabilities and aesthetic preferences. In someembodiments, the party information component can utilize user input orusage history to select particular information to present or orderspecific information from query results. Similarly, in some embodiments,the party information component can utilize user input or usage historyto override, remove or reorder query results, and perform a default orspecified action. Some embodiments performing multiple queries canutilize the party information component to compare information frommultiple queries to determine importance or veracity of specific queryresult content. In some embodiments, the party information component canbe toggled on or off. The party information component or any otherfeature of an associated system can include an opt-in/opt-out aspectthat can be determined at the time of purchase, activation, or any latertime.

In addition, some embodiments can utilize the party informationcomponent on multiple networks or with multiple means of data exchange.The party information component can also function in combination withmultiple databases. In some instances, the party information componentcan select or deselect particular communication channels or databaseswith which to operate.

In some embodiments, the party information component can manageinformation to present additional information relating to data earlierpresented to an operator of a user device. In some embodiments, relevantfurther information can be stored from an earlier query for recall ordisplay when further information is sought. An operator of a user devicecan select, toggle or otherwise offer input to commence retrieval offurther information, or the party information component can retrievefurther information without user action. Further or additionalinformation can include greater detail about one or more of identifyinginformation relating to another party to a communication and an itemretrieved from an earlier query, including but not limited to phonenumbers and extensions thereof such as area codes, as well asinformation about associated or nearby numbers; physical addresses andextensions thereof such as zip codes, as well as information about thelocation or points of interest nearby; electronic addresses andextensions thereof such as domains, gateways, hardware addresses oridentifiers and networks; messaging names and related information suchas service information; information about an individual and theirrelations, an organization and its associations, or generally relevantto an entity of interest; and other information about items displayed orqueried in response to a communication. The previous examples ofpossible additional and further information are not intended to be anexhaustive list of options, but are illustrative of the sort of data auser might commonly seek in response to communication.

The party information component can also facilitate caching in someembodiments. In one embodiment, all query results can be cached on theuser device. In other embodiments, query results can be cached in aremote location separate from the device, or partially cached in adistributed fashion on several components or devices. In anotherembodiment, a cache can be or act as a database to be queried. Someembodiments can employ a separate history, through which an operator ofa user device can browse. History items can be selected to facilitatepersistence of specific query results in a user device store (e.g.,commit to entry of address book, save to media card, add to database onremote drive, et cetera).

Display and utilization of information managed by the party informationcomponent can be improved with an information interface component. Insome embodiments, the party interface component can facilitate or beoperable in conjunction with such the information interface component.In some embodiments, the party information component and informationinterface component can be dynamic and interactive, facilitatingretrieval of further information on a topic or issue presented by thedisplay. In some embodiments, the information interface component canchange or update the displayed information to convey additionalinformation to an operator of a user device without requiring input or astate change.

In some embodiments the information interface component can leverage thenative display and control functionality of a device or component. Inother embodiments, the information interface component can be astandalone or nonresident component used in conjunction with a device orinfrastructure. The information interface component can displayinformation retrieved by the party information component. Theinformation interface component can aid the party information componentin preparing content for display, or prepare such content independently.In some embodiments, the information interface component can displaystatic content, dynamic content, and any combination thereof.

The information interface component can facilitate user interaction withdisplayed information. In some embodiments, the information interfacecomponent can allow a user or system to request more information aboutdisplayed content. The information interface component can allowselection or manipulation of displayed content in a fashion similar tothat employed by a device used in conjunction with the informationinterface component. In some embodiments, the information interfacecomponent can utilize its own control scheme which is different fromthat employed by a device used in conjunction with the informationinterface component.

One or more embodiments can employ a query component to perform databasequeries. The query component utilizes known information relating to acommunication party to perform a query of one or more databases todiscover information about the communication party. The query resultsare returned to the party information component or another component formanaging such results. The query component can also perform subsequentqueries to discover additional information about the communicationparty, test the veracity of known information about the communicationparty, or search for further information relating to items alreadydisplayed on a communication device. The query component may querysubstantially any available database by substantially any communicationmeans or combination of communication means available.

The query component can be co-located with the party informationcomponent and information interface component, or can be embodied onanother component within the communication path. Several querycomponents can exist (e.g., one embodied in a mobile device and oneembodied in a base station) where such redundancy would benefit anembodiment. The query component can perform a database query prior tosetting up communication, once communication is established, aftercommunication, or at substantially any time. The query component canperform multiple queries at once, or can perform additional queriesafter one is complete. Initial or subsequent queries can be commencedwith our without user input, or with or without a state change in thedevice or data.

Turning now to the figures, FIG. 1 illustrates an example system 100that can return data relevant to a telephone call on a user device 110.User device 110 is can communicate with at least a telephone service 120and a data gateway 130. In some embodiments, the user device 110 can usea single means of communication to connect to telephone service 120 anddata gateway 130. In other embodiments, telephone service 120 and datagateway 130 can be co-located, or can exist as a single devicefacilitating both functions. In some embodiments, telephone service 120and/or data gateway 130 can be one or more service control points (SCP)or similar nodes. User device 110 can employ multiple means ofcommunication, to include any means of voice and data transmission. Instill other embodiments, telephone service 120 can represent a telephoneswitch, service control point, service switching point, service transferpoint, and similar node, or a plurality thereof.

User device 110 exchanges messages by receiving data from another useror device, or sending data to another user or device. In example system100, an operator of user device 110 can receive or locate furtherinformation relating to other communication parties with which the userdevice 110 exchanges messages. Data gateway 130 can access database 140.Database 140 can be a single database or a plurality of databases.Database 140 can exist in a single location as a private or proprietarydatabase, or a distributed database such as a local area network or theInternet. Database 140 can be co-located with data gateway 130, or bothcomponents can be embodied in a single component. It is to be understoodthat database 140 need not be a single component, but is used torepresent any non-locally stored (e.g., in-the-cloud storage)information available to an operator of user device 110 throughavailable components and infrastructure. Database 140 can be adistributed system or network, or a means for searching or managing suchdistributed system or network. Alternatively, or in addition, database140 can be a proprietary database (e.g., corporate directories andcommercial compilations) or traditional calling name database similar tothose used by phone companies to enable Calling Name calleridentification on landline telephones.

After user device 110 engages in communication, information about thecommunication can be discovered from querying database 140. In someembodiments, the communication can be a telephone call received ordialed. In some embodiments, the communication can be a text-basedcommunication, such as a text message or e-mail. In other embodiments,the communication can be a multimedia or mixed-content message. Queryingdatabase 140 involves at least requesting information relating toanother party or a plurality of parties with whom an operator of userdevice 110 is communicating with or has communicated with. At least theother parties' known identifying information (as described above) isincluded in the query of database 140. Information germane to theparties or communication from database 140 is returned to user device110.

FIG. 2 illustrates an additional example system 200 that facilitatesreturning information to user device 210 during communication with otheruser devices. Data gateway 230 provides access to network 250. Network250 can be a single network or plurality of networks. Network 250 inturn provides access to plurality of databases 240 (e.g., a datawarehouse), which includes a set of N databases 242 ₁-242 _(N) (N is apositive integer). It should be appreciated that one or more oftelephone service 220, data gateway 230, plurality of databases 240 andnetwork 250 can be co-located or realized through a single component.

In an aspect of the subject innovation, when data gateway 230 is anInternet gateway providing access to the Internet network 250, pluralityof databases 240 can be substantially any stored information, as it isunderstood that search engine and aggregation services (e.g., Google,Yahoo!, the Internet Archive, torrents, and peer-to-peer services) canquery, cache or otherwise utilize virtually any document or file on theInternet. It is further understood that example system 200 is notlimited to querying data through a single means where multiple means areavailable. The user device 210, data gateway 230, plurality of databases240, and network 250 can all be enabled to request or perform one ormore queries. It is noted that telephone service 220 can also perform orfacilitate queries. Queries can be performed with more than one search,index and request to locate other results or compare similar results.Multiple queries can be performed in the same manner on a singledatabase (e.g., several Google searches on one domain), or multiplemeans of query can be employed on a single database within plurality ofdatabases 250 (e.g., Yahoo! search and a software index search on asingle domain). The same query options can be extended to more than oneor all databases within the plurality of databases 250.

Turning now to FIG. 3, an example system 300 for returning informationrelevant during mobile communications is illustrated. Mobile device 310can be a cellular telephone, smart phone, PDA, pager, radio component,or other mobile unit capable of transmitting and receiving information.Mobile device 310 is understood to have a user interface (includingmeans for display and control) and at least one means for communication.In some embodiments, mobile device 310 can additionally include meansfor storage (local, remote, and/or distributed fixed and/or removablemedia). Mobile device 310 connects to telephone service 320 and datagateway 330 via base station 370.

In the illustrated example, communication party 360 can place a call(e.g., a voice call or data session) via communication link 362 to anoperator of mobile device 310. In alternative embodiments, an operatorof mobile device 310 can dial communication party 360, or either partycould initiate another electronic correspondence (e.g., communication asdescribed above). In conventional systems, mobile device 310 typicallydisplays the telephone number of communication party 360. System 300enables mobile device 310 to receive and provide substantially richerinformation related to communication party 360 through data returnedfrom database 340. In example system 300, when communication party 360dials an operator of mobile device 310, the call is routed through thetelephone network using telephone service 320. A call utilizingtelephone service 320 is routed through to base station 370 whichmaintains a wireless communication link 312 with mobile device 310. Itis understood that base station 370 can be a plurality of base stationsif mobile device 310 is in handoff or has completed handoff. In someembodiments, base station 370 can represent multiple base stations wheremobile device 310 transitions between areas of coverage (or undergoeshandoff). A telephone call from communication party 360 will generallyonly include information relating to number from which communicationparty 360 is calling. Example system 300 facilitates querying database340 to discover further information relating to the telephone numbercurrently associated with communication party 360.

In some embodiments, base station 370 is enabled to initiate a query ofdatabase 340 on behalf of mobile unit 310 when incoming communicationfrom communication party 360 is received. In other embodiments, thequery can be performed by another component of the system, such as datagateway 330, in which case base station 370 can pass notification of thepending communication to data gateway 330 to initiate a query. In stillother embodiments, mobile device 310 initiates a query after receiving atransmission request or other data notifying communication from basestation 370.

Once query of database 340 is complete, the results of the query arereturned to network 350, through data gateway 330, to base station 370.In some embodiments query results can be directed to base station 370via telephone service 320 if possible or another component besides or inaddition to data gateway 330. Base station 370 can then transmit thequery results to mobile device 310 using an existing communicationchannel or another channel that becomes available. The results of thequery of database 340 can be transmitted at any time after thecommunication is initiated. In the situation where the communicationbetween an operator of user device 310 and communication party 360 is atelephone call, mobile device 310 could be provided with query resultsimmediately before the call is answered, during the call, and after thecall is terminated. Alternatively, the query results could be savedpresented or recalled at a later time.

Turning now to FIG. 4, an example system 400 is illustrated wherebyadditional information such as calling name is provided to users ofVoice-over-Internet-Protocol (VOIP) systems. In embodiments, system 400can also be applied to SIP phone systems. In some VOIP systems, callingname or data other than the number or address of a communicationparticipant was only available if the communication participant was amember of the same service or if the VOIP service had access to aproprietary database similar to those employed by traditional phonecompanies. System 400 allows utilization of network 430 to querydatabase 440 while concurrently establishing the VOIP telephone linkthrough telephone service 420.

In one embodiment, communication party 460 places a call to an operatorof telephone 410. Communication party 460 can initiate or receivecommunication via communication link 462. If communication party 460 isutilizing a traditional landline telephone, the call will be routedthrough telephone service 420, eventually to network 430. VOIP component450 receives the call through network 430, and notifies an operator oftelephone 410. Telephone 410, VOIP component 450, software or hardwareassociated with network 430, or any combination thereof, can initiate aquery of database 440 using network 430. In some embodiments, VOIPcomponent 450 or telephone 410 can have additional communication meansbeyond network 430, which can also be employed to initiate a query.Additionally, some embodiments can enable another device (e.g., personalcomputer) to manage call information or initiate a query. Informationabout communication party 460 discovered via database query is returnedto an operator of user telephone 410. Query results can return by thesame path of the query request, or by any other communication meansavailable. Query results can be display on telephone 410 as calleridentification information, or on any other display interface availableto an operator of telephone 410 sharing communication links with othercomponents of system 400. Query results can be displayed simultaneouslywith notification of a call, during a call, after a call, or at a latertime when requested by an operator of telephone 410.

In another embodiment, telephone 410 places a call to communicationparty 460. As described in the above embodiment, telephone 410, VOIPcomponent 450, or components of network 430 can query database 440 forinformation relating to communication party 460 to return to theoperator of telephone 410. Query results are returned to an operator oftelephone 410. In one embodiment, query results can be returned to anoperator of telephone 410 who is dialing as soon as dialing is complete.In other embodiments, results can be returned to an operator oftelephone 410 during the call, after the call, or can be accessed at alater time.

Telephone 410 and VOIP component 450 will collectively include at leastuser control and display interfaces, storage, and connectivity tonetwork 430. In some embodiments, telephone 410 represents multipletelephones sharing a common line of communication. VOIP component 450can include, but is not limited to, analog terminal adapters (ATAs),personal or distributed computers, modems, routers, hubs, and commoncomponents of telephone or network systems, realized through hardware,software or a combination thereof.

In an aspect of the subject innovation, telephone service 420 canprovide a VOIP interface (not shown) which can facilitate an all-VOIPcommunication among parties that utilize network-based voicecommunication(s). In other embodiments, VOIP component 450 can beintegrated into other components, or alternatively can comprise aplurality of components. While illustrated example system 400 isdirected toward a diverse communication that employs both VOIP andtraditional landline telephones, it is to be appreciated that extensionsto example system 400 can allow communication via other arrangements oranalogous communication services (e.g., Skype™, Ventrilo, signalrepeaters such as Radio over Internet Protocol, corporate voice systems,click-to-talk, et cetera). Similarly, example system 400 also can beextensible to non-voice communications (e.g, data sessions) over one ormore networks. In some embodiments, example system 400 can provide datarelevant to communication party 460 not only for realtime voicecommunication, but also for other communication (as communication isdescribed above) routed through network 430. It is additionallyunderstood that some telecommunications networks can include additionalcomponents not illustrated in system 400, and can combine or excludecomponents illustrated in system 400, while still enabling substantiallyequivalent functionality.

FIG. 5 illustrates yet another example system 500 which facilitatesadditional information related to a communication provided to anend-user of satellite phone 510. Satellite phone 510 engages in two-waycommunication with satellite 580 via communication link 584. Satellite580 also engages in two-way communication with earth station 570 viacommunication link 582. Earth station 570 provides access to datagateway 530 and telephone service 520. Telephone service 520 enablesconnection to users of traditional landline telephones or usersemploying alternative telephone systems. Communication party 560 isengaged in communication with satellite phone 510, and can utilize amobile communication device or a non-mobile communication devicecommunicating in part via communication link 562. Data gateway 530allows communication with users engaged in correspondence via datatransmissions. Data gateway 530 additionally enables access to network550, which in turn provides access to database 540. Database 540 is forinformation relating to communications in which the operator ofsatellite phone 510 participates.

Communication link 584 and communication link 582 provide satellitesupport to satellite phone 510 and earth station 570. Example system 500can utilize applications requiring satellite support via communicationlink 584 and 582. For example, satellite phone 510 is not constrained toany particular network to perform lookup of information relating tocommunication party 560. Support for information lookup is thusuniversal and independent of available local networks. Satellite 580 canalso provide enhanced location based services and other featurescommonly associated with satellite uplink.

It is understood that system 500 is illustrative, and substantiallyanalogous systems can include other known components not pictured insystem 500. Analogous systems can also exclude or combine componentspictured in system 500. For example, satellite 580 can facilitate directcommunication between satellite phone 510 and another satellite-enableddevice. In one such embodiment, satellite 580 can still connect to earthstation 570 to facilitate access to data gateway 530 and network 550 toquery database 540 for further information relating to a communicationutilizing satellite phone 510. In other embodiments, additional relayscan be used to transmit a signal. In one such embodiment, satellite 580can represent a plurality of satellites, or earth station 570 canrepresent a plurality of earth stations. In embodiments where satellite580 represents a plurality of satellites, or in embodiments where earthstation 570 represents a plurality of earth stations, such pluralitiescan perform relay functions, facilitate retention of coverage (e.g.,through handoff), and provide overlapping coverage (e.g., overlappingsatellite beams, earth station coverage areas).

Turning now to FIG. 6, an example embodiment 600 a data gateway isillustrated in accordance with aspects of the subject innovation. Asdiscussed supra, several components utilized in one or more embodimentscan be combinations of a plurality of components, or advantageousexpansions or modifications of a single component. For example, in someembodiments of example systems described herein, data gateway 610 caninclude a gateway connector 612 and a network connector 614 bridging aconnected device to service provider 616. In some embodiments, gatewayconnector 612 connects to a data gateway or base station which relaysnetwork transmissions to a user device elsewhere. In other embodiments,a user device can connect directly to gateway connector 612. Gatewayconnector 612 then provides the link for any external devices to networkconnector 614, which provides access to service provider 616. Serviceprovider(s) 616 can represent one or more service providers, includingbut not limited to home or corporate networks, commercial Internetservices such as America Online™ or NetZero™, another means ofconnecting to the Internet, remote system access, peer-to-peer or ad hocnetworks, and distributed computing environments. System 600 is only oneexample of how substantially analogous systems can include or excludecertain components to the accomplishment of these ends.

By employing gateway connector 612 and network connector 614, datagateway 600 is provided access to networks otherwise not available.Further, gateway connector 612 and network connector 614 facilitateaccess to content specific to service provider(s) 616. For example, ifany one of service provider(s) 616 allows access to a provider database(e.g., member directory, private knowledge-base, private storage), datagateway 600 now provides a link to such provider content. In this way,data gateway 600 can facilitate information lookup in both public andnon-public databases.

FIG. 7 includes a system 700 illustrating one embodiment of a possibleuser interface to display information resulting from database queryabout an incoming or outgoing call or communication. User device 710includes device display 712. When user device 710 is engaged incommunication, device display 712 shows telephone number 714, as inconventional systems. Telephone number 714 can be any telephone numberfrom any country and in any format supported by user device 710.Telephone number 714 additionally need not be a telephone number wherecommunication is not a telephone call or SMS message. For example, whereuser device 710 is engaged in instant messaging or e-mail, an address oruser name can be substituted. In addition to telephone number 714,device display 712 can also show a name 716 associated with telephonenumber 714. Name 716 can be, but is not limited to, an individual name,family name, business or organization name, title, and other string ofcharacters associated with the number or address associated with thecommunication.

In the same manner, some embodiments can also display furtherinformation 718 when it is discoverable via the available query means.For example, search engines such as Google or Yahoo! include directorieswhich can display phone numbers and addresses for certain users in avariety of databases. In addition, these search engines have access tosites containing business and biographical information, and maps andother location based services. In system 700, further information 718can display an address associated with the phone number of name involvedin the communication, or can enable the user to search until suchinformation is returned. Further information 718 can also contain moregeneral information gleaned from an area or country code associated withthe telephone number. In embodiments utilizing system 700 with othermeans of communication, at least a portion of further information 718could be inferred from an originating or target domain or messengerservice.

Further information 718 could employ returned biographical informationto provide additional details, such as, but not limited to, occupation(e.g., musician), organization or family information, relevant newsitems, associations, known relations, and any number of other recordableattributes from available public or private databases. Embodimentscombined with social networking technologies can display commonacquaintances or other relations in further information 718. Someembodiments can also implicitly link known entities by proximity (e.g.,same area code, zip code, network address, et cetera) and other means.

Where either specific or general location information is included infurther information 718, some embodiments can include location basedservices to increase the functionality of the interface provided on thedevice display 712. If user device 710 includes self-locating technology(e.g., devices enabled to utilize GPS, signal propagation, andtriangulation techniques), further information 718 can include theability to plan a route to a referenced location. In embodiments whichdo not include self-locating technology, further information can enableoperators of user device 710 to generate directions with additionalinput. Further information 718 can also include functionality to locatepoints of interest nearby a referenced location.

In some embodiments, items displayed on device display 712 (e.g.,telephone number 714, name 716, further information 718) will beselectable to locate additional information on any particular item. Someembodiments can include buttons 720 (or other selectable display itemsincluding but not limited to links, menus, windows and tabs) to requestfurther information about a particular display item. In someembodiments, the items (e.g., telephone number 714, name 716, furtherinformation 718) themselves can be selectable links. Specificembodiments can allow items to be selected at different times or at anytime. For example, some embodiments can allow an operator of user device710 to select items as soon as a communication is received but beforeanswering. Other embodiments can also allow, or exclusively allow, anoperator of user device 710 to select items after answering acommunication, during communication, after communication, or at a latertime.

In some embodiments, the operator of user device 710 can prefer todisplay specific information about another party to a communication. Forexample, user device 710 or components connected to user device 710 canalready include or have access to stored information (e.g., in anaddress book, directory, contact history, cache) relating to a specifictelephone number or address (e.g., name, nickname, specificbiographical, business, or location information). In some embodiments,such information can be preferred over other information located in aqueried database, and can be displayed on device display 712 prior toquerying a database for additional information, or regardless of whatinformation is returned from a database query. In other embodiments,where only certain stored information is preferred, unused portions ofdevice display 712 can still show more information discovered as aresult of a database query.

Turning now to FIG. 8, example method 800 is illustrated for providing auser device engaged in communication with additional informationrelating to that communication. At 810, a communication is set up. Thecommunication set up at 810 can be any interparty communication asdescribed above. In some embodiments, method 800 is applied to multipleparties in a communication involving more than two parties.

At 820, a database is queried. At least a portion of the query terms caninclude at least a portion of identifying information (as describedabove) for another party to the communication set up at 810. In someembodiments, more than one database can be queried. In some embodiments,more than one query can be processed on one or more databases. Inembodiments processing multiple queries, more than one means of querycan be utilized. The database query at 820 can return informationrelating at least in part to the identifying information of anotherparty to the communication. At 830, a determination is made as towhether relevant information has been returned via the database query at820. If database query 820 fails to return acceptable results, defaultinformation is displayed at 840. Default information displayed at 840can include the identifying information used in the database query.

Conversely, if the query results contain relevant information, suchdatabase information is displayed at 850. The display can exhibitresults similarly, or can present specific items in different formats.In addition to aesthetic features, display of database information at850 can be altered or formatted to facilitate compatibility according toresources and settings, such as but not limited to available user devicehardware, screen area, controls, and explicit or inferred system ornetwork preferences.

FIG. 9 illustrates example method 900 providing an alternative, oradditional, embodiment of a methodology for querying informationrelating to a party to a communication. A communication is set up at910. At 920, information at least in part including at least a portionof identifying information is compared against local or remote storageto determine if data is already known relating to the other party to acommunication. Such data can exist on a user device, or on a componentor network accessible to the user device. A party to a communication canbe known literally or constructively; an operator of a user device canliterally know a communication party and can store a name, nickname orother idiosyncratic information, organization, and other relevantinformation in a local or remote address book or other store associatedwith at least a portion of identifying information related to the partyto the communication; or constructively, wherein previous query resultscan still be stored and easily recalled even if not committed to anaddress book or even actively viewed by the operator of the user device.If such information is discovered at 920, information from storage canbe displayed at 940.

If no relevant information exists in existing storage, at 930 a databasewill be queried. At 950, it is determined whether relevant data wasdiscovered via the database query. If not, default information will bedisplayed at 960. If relevant information is returned as a result of thedatabase query at 930, the database information will be displayed at970.

FIG. 10 illustrates another embodiment of an example method 1000 forproviding information relating to a party to a communication. At 1010, acommunication is set up. A determination is made at 1020 as to whetherinformation relating to the party to the communication already exists instorage. If pertinent stored information exists, it can be displayed at1030. If no stored information relating to the party to thecommunication exists, a database can be queried at 1040. At 1050, adetermination is made as to whether data relating to the party to thecommunication was returned from the database. If data is not found, adefault display can be shown at 1060. If applicable information isreturned with the database query, these results can be stored at 1070.At 1080, the now-cached database query results can be displayed to anoperator of a device. In another embodiment of example method 1000, theadditional aspect of allowing an operator of a user device to browsethrough a query result history and save selected results can beincluded.

FIG. 11 illustrates example method 1100 for showing information relatingto a communication according to user preferences. At 1110, acommunication is set up. At 1120, a determination is made as to whetherthe user has a preference for display relating to this communication(based on e.g., type of communication, identifying information relatingto another party of the communication, preferred display setup, etcetera). If a user preference exists, the display is presented at 1140according to user preference. If no preference exists, a database queryoccurs at 1130. At 1150, a determination is made as to whether pertinentinformation was returned from the database query. If so, the databaseinformation can be displayed at 1170. If no relevant information isdiscovered via the database query at 1140, a default display can bepresented at 1160.

FIG. 12 illustrates an embodiment of an example method 1200 fordisplaying additional data relating to information previously presentedrelating to a communication. At 1201 information relating at least inpart to identifying information associated with a party to acommunication is displayed. In some embodiments, the previouslypresented information can be decomposed before additional information isrequested (e.g., search for more information about a particular areacode, as opposed to the entire telephone number). Thereafter, furtherinformation can be requested. At 1210, it is determined if furtherinformation is requested. If no further information is requested, a userdevice can continue or resort to default behavior at 1220.

If, at 1210, a determination is made to seek further information, asearch for additional information can proceed at 1230. Additionalinformation can be requested with (e.g., clicking for ‘More Info’) orwithout (e.g., pull data similar to that of the last several calls)input from an operator of a user device. The search can occur utilizingany available database or storage. The database or storage can be aplurality of databases or storage, and combinations thereof, and canalso be local, remote, and distributed across a combination of local andremote components. The search at 1230 can be one or more searches by oneor more methods on one or more databases and storage components. Adetermination is made as to whether relevant information was discoveredvia the search at 1240. If no further information was found, a defaultdisplay can be employed at 1250. If additional relevant informationexists in the search results, the search data can be displayed at 1260.In some embodiments, the results of a request for additional informationcan display in a screen associated with the communication, a userinterface or control screen. In other embodiments, a web browser, mediaplayer, content display component, and other applications can beutilized to navigate or exhibit additional information. In someembodiments, additional information can be cached or stored. Certainembodiments allow additional information to be appended to acommunication underway or forwarded to another entity in a separatecommunication.

To provide further context for various aspects of the subjectspecification, FIG. 13 illustrates a block diagram of an exampleembodiment 1300 of a mobile device 1310 that can handle informationrelating to another communication party in accordance with aspectsdescribed herein. Additionally, FIG. 14 presents a block diagram of anexample embodiment 1400 of a device 1405, which can be provisionedthrough a non-mobile network platform, and can manage informationrelating to another communication party as described herein.Furthermore, FIG. 15 presents an example embodiment 1500 of a mobilenetwork platform 1510 which can facilitate communication andtransmission of information relating to parties involved in thecommunication in accordance with aspects described herein.

In mobile device 1310, which can be a multimode access terminal, a setof antennas 1369 ₁-1369 _(K) (K is a positive integer) can receive andtransmit signal(s) from and to wireless devices like access points,access terminals, wireless ports and routers, and so forth, that operatein a radio access network, e.g., RAN 185. It should be appreciated thatantennas 1369 ₁-1369 _(K) are a part of communication platform 1325,which comprises electronic components and associated circuitry thatprovide for processing and manipulation of received signal(s) andsignal(s) to be transmitted. In an aspect, communication platform 1325includes receiver(s)/transmitter(s) 1366 that can convert signal fromanalog to digital upon reception, and from digital to analog upontransmission. In addition, receiver/transmitter 1366 can divide a singledata stream into multiple, parallel data streams, or perform thereciprocal operation; such operations typically conducted in variousmultiplexing schemes. Functionally coupled to receiver(s)/transmitter(s)1366 is a multiplexer/demultiplexer (mux/demux) component 1367 thatfacilitates manipulation of signal in time and frequency space.Electronic mux/demux component 1367 can multiplex information(data/traffic and control/signaling) according to various multiplexingschemes such as time division multiplexing (TDM), frequency divisionmultiplexing (FDM), orthogonal frequency division multiplexing (OFDM),code division multiplexing (CDM), space division multiplexing (SDM). Inaddition, mux/demux component 1367 can scramble and spread information(e.g., codes) according to substantially any code; e.g., Hadamard-Walshcodes, Baker codes, Kasami codes, polyphase codes, and so on. Amodulator/demodulator (mod/demod) component 1368 is also a part ofcommunication platform 1325, and can modulate information according tovarious modulation techniques, such as frequency modulation (e.g.,frequency-shift keying), amplitude modulation (e.g., M-ary quadratureamplitude modulation (QAM), with M a positive integer; amplitude-shiftkeying (ASK)), phase-shift keying (PSK), and the like. In an aspect ofembodiment 1300, mod/demod component 1368 is functionally coupled tomux/demux component 1367.

In embodiment 1300, multimode operation chipset(s) 1315 allows mobiledevice 1310 to operate in multiple communication modes in accordancewith disparate technical specification for wireless technologies. In anaspect, multimode operation chipset(s) 1315 utilizes communicationplatform 1325 in accordance with a specific mode of operation. Inanother aspect, multimode operation chipset(s) 1315 can be scheduled tooperate concurrently (e.g., when K>1) in various modes or within amultitask paradigm.

Mobile device 1310 can include party information component 1318 andinformation interface component 1319 which can transmit and receive inaccordance with and to facilitate aspects described in the subjectspecification.

Mobile device 1310 also includes a processor 1335 configured to conferfunctionality, at least in part, to substantially any electroniccomponent within mobile device 1310, in accordance with aspects of thesubject innovation. As an example, processor 1335 can be configured toexecute, at least in part, instructions in multimode operationchipset(s) that afford multimode communication through mobile device1310 like concurrent or multitask operation of two or more chipset(s).As another example, processor 1335 can facilitate mobile device 1310 toreceive traffic (e.g., various data flows) and relay such traffic viacommunication platform 1325. As yet another example, processor 1335 canreceive synchronization indications to maintain content synchronizedwith operation performed in a device (not shown) attached to mobiledevice 1310. It should be appreciated that processor 1335 can store(e.g., in cache memory) at least temporarily traffic received fromeither extension interface 1318 or communication platform 1325, or both.Moreover, processor 1335 facilitates mobile device 1310 to process data(e.g., symbols, bits, or chips) for multiplexing/demultiplexing,modulation/demodulation, such as implementing direct and inverse fastFourier transforms, selection of modulation rates, selection of datapacket formats, inter-packet times, et cetera. Memory 1355 can storedata structures (e.g., metadata); code structure(s) (e.g., modules,objects, classes, procedures) or instructions; network or deviceinformation like policies and specifications, attachment protocols; codesequences for scrambling, spreading and pilot (e.g., referencesignal(s)) transmission; frequency offsets, cell IDs, and so on.

In embodiment 1300, processor 1335 is functionally coupled (e.g.,through a memory bus) to memory 1355 in order to store and retrieveinformation necessary to operate and/or confer functionality, at leastin part, to communication platform 1325, multimode operation chipset(s)1315, extension interface 1318, and other operational aspects ofmultimode mobile device 1310.

FIG. 14 is a block diagram of an example embodiment 1400 of a devicethat can manage information relating to a communication party asdescribed herein. Device 1405 includes a functional platform 1415 thatcomprises a set of components that provide, at least in part, one ormore specific functionalities of the device 1405. Additionally, device1405 includes a party information component 1425 and an informationinterface component 1426 in accordance with aspects described herein.Moreover, in an aspect, device 1405 can include a communication platform1465 that can provide wireless communication capabilities in addition,or alternatively, to connectivity of device 1405 through wired links(e.g., Ethernet, USB, GPIB, RS-232, FireWire, optical or coaxial cable,or router (not shown)). With respect to wireless capability, in device1405, which can be a multimode access terminal, a set of antennas 1467₁-1467 _(K) (K is a positive integer) can receive and transmit signal(s)from and to wireless devices like access points, access terminals,wireless ports and routers, et cetera, that operate in a radio accessnetwork (e.g., RAN 185). Communication platform 1465 can exploit the setof K antennas 1457 ₁-1457 _(K), (K is a positive integer) to establishcommunication within various modes such as single-input single-output,or multiple-input multiple output. Communication platform 1465 operatesin substantially the same manner as communication platform 1325.

Additionally, in device 1405, a peripheral component 1435 can include,or facilitate connection to, additional devices such as printer(s),media player(s), wireless router(s), network interfaces, biometricstouch-pad(s), et cetera. In an aspect, to afford such connectivity,peripheral component 1435 can include jacks for one or more of Ethernet,USB, GPIB, RS-232, FireWire, optical or coaxial cable connectors.Additionally, display interface 1455 can be a part of functionalplatform 1415 (e.g., when device 1405 is a PC, an IPTV interface, amobile, a backprojector component, a data projector . . . ). Displayinterface 1455 also can display functions that control functionality ofdevice 1405, or reveal operation conditions thereof (e.g.,light-emitting-diode (LED) indicator(s) of devices operable with anetwork and available for content transaction(s)). In an aspect, displayinterface 1455 can be a liquid crystal display (LCD), a plasma panel, amonolithic thin-film based electrochromic display, and so on.

It should be appreciated that device 1405 also can include a data entryinterface 1445 that can allow an end user to perform at least one of (i)command device 1405 via configuration of functional platform 1415, (ii)interact with a provisioning network platform (e.g., an enterprisenetwork platform) or with a mobile network platform.

Power supply 1475 can power-up device 1405 and substantially anycomponent included thereon. It should be appreciated that alternative oradditional embodiments of device 1405 may not include power supply 1475and be powered via an attachment to a conventional power grid.

In embodiment 1400, device 1405 includes processor 1485 which can befunctionally coupled (e.g., through a memory bus) to memory 1495 inorder to store and retrieve information necessary to operate and/orconfer functionality, at least in part, to client component 1425, andsubstantially any component thereon in accordance with aspects describedherein; functional platform 1415, communication platform 1465 whendevice 1405 includes it; and substantially any other component of device1405. In addition, in connection with communication platform 1465,device 1405 also includes a processor 1485 configured to conferfunctionality, at least in part, to substantially any electroniccomponent within device 1405, in accordance with aspects of the subjectinnovation. As an example, processor 1485 can be configured to execute,at least in part, instructions in multimode operation chipset(s) thatafford multimode communication through device 1405 like concurrent ormulti-task operation of two or more chipset(s). It should be appreciatedthat processor 1485 can store (e.g., in cache memory) at leasttemporarily traffic received from communication platform 1425, or both.Moreover, processor 1485 facilitates device 1405 to process data (e.g.,symbols, bits, or chips) for multiplexing/demultiplexing,modulation/demodulation, such as implementing direct and inverse fastFourier transforms, selection of modulation rates, selection of datapacket formats, inter-packet times, et cetera.

Memory 1495 can store data structures (e.g., metadata); codestructure(s) (e.g., modules, objects, classes, procedures) orinstructions, or substantially any type of software or firmware thatprocessor 1485 can execute to provide functionality associated withfunctional platform 1415; network or device information like policiesand specifications; code sequences for scrambling, spreading and pilot(e.g., reference signal(s)) transmission; and so on. Additionally,memory 1495 also can retain content(s) (e.g., multimedia files),historic data on content transaction(s), security credentials (e.g.,passwords, encryption keys, digital certificates, biometric referenceindicators like voice recordings, iris patterns, fingerprints), etcetera.

As indicate supra, FIG. 15 presents an example embodiment 1500 of amobile network platform 1510 which can register transmit informationrelating to communication parties in accordance with aspects describedherein. Generally, mobile network platform 1510 can include components,e.g., nodes, gateways, interfaces, servers, or platforms, thatfacilitate both packet-switched (PS) (e.g., internet protocol (IP),frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS)traffic (e.g., voice and data) and control generation for networkedwireless communication. In an aspect of the subject innovation, mobilenetwork platform 1510 includes CS gateway node(s) 1512 which caninterface CS traffic received from legacy networks like telephonynetwork(s) 1540 (e.g., public switched telephone network (PSTN), orpublic land mobile network (PLMN)) or a SS7 network 1560. Circuitswitched gateway node(s) 1512 can authorize and authenticate traffic(e.g., voice) arising from such networks. Additionally, CS gatewaynode(s) 1512 can access mobility, or roaming, data generated through SS7network 1560; for instance, mobility data stored in a visited locationregister (VLR), which can reside in memory 1530. Moreover, CS gatewaynode(s) 1512 interfaces CS-based traffic and signaling and gatewaynode(s) 1518. As an example, in a 3GPP UMTS network, CS gateway node(s)1512 can be embodied, at least in part, in gateway GPRS support node(s)(GGSN). In an aspect, CS gateway node(s) can embody, at lease in part,gateway node(s) 165.

In addition to receiving and processing CS-switched traffic (e.g.,content(s) that can be part of a content transaction) and signaling, PSgateway node(s) 1518 can facilitate PS-based data sessions with served(e.g., through RAN 185) mobile devices, or with other devices. Partyinformation component 1517, which is substantially the same as the partyinformation component described elsewhere herein, can utilize these andother components of mobile network platform 1510 to realize aspectsdisclosed herein. Data sessions can include traffic, or content(s),exchange with networks external to the mobile network platform 1510,like wide area network(s) (WANs) 1550; it should be appreciated thatlocal area network(s) (LANs) 1570 can also be interfaced with mobilenetwork platform 1510 through PS gateway node(s) 1518. It is to be notedthat WANs 1550 and LANs 1570 can embody, at least in part, servicenetwork(s) 170. Packet-switched gateway node(s) 1518 generates packetdata contexts when a data session is established. To that end, in anaspect, PS gateway node(s) 1518 can include a tunnel interface (e.g.,tunnel termination gateway (TTG) in 3GPP UMTS network(s) (not shown))which can facilitate packetized communication with disparate wirelessnetwork(s), such as Wi-Fi networks. It should be further appreciatedthat the packetized communication can include multiple flows that can begenerated through service (e.g., provisioning) and application server(s)1514. It is to be noted that in 3GPP UMTS network(s), PS gateway node(s)1018 (e.g., GGSN) and tunnel interface (e.g., TTG) comprise a packetdata gateway (PDG).

In embodiment 1500, mobile network platform 1510 also includes servingnode(s) 1516 that convey the various packetized flows of data streams(e.g., content(s) that are part of content transaction(s)), receivedthrough PS gateway node(s) 1518. As an example, in a 3GPP UMTS network,serving node(s) 1516 can be embodied in serving GPRS support node(s)(SGSN). In an aspect, serving node(s) 1516 can embody, at least in part,service providers or networks as disclosed elsewhere herein.

Server(s) 1514 in mobile network platform 1510 can execute numerousapplications (e.g., communication services, location services, onlineapplications and entertainment, wireless device management, et cetera)that can generate multiple disparate packetized data streams or flows,and manage (e.g., schedule, queue, format . . . ) such flows. Suchapplication(s), for example can include add-on features to standardservices provided by mobile network platform 1510. Data streams (e.g.,content(s) that are part of a content transaction) can be conveyed to PSgateway node(s) 1518 for authorization/authentication and initiation ofa data session, and to serving node(s) 1516 for communicationthereafter. As discussed above, PS gateways node(s) 1518 can convey thedata streams (e.g., content(s)) to a device (e.g., device J 105 _(J)).Server(s) 1514 can also effect security (e.g., implement one or morefirewalls) of mobile network platform 1510 to ensure network's operationand data integrity in addition to authorization and authenticationprocedures that CS gateway node(s) 1512 and PS gateway node(s) 1518 canenact. Moreover, server(s) 1514 can provision services from externalnetwork(s), e.g., WAN 1550, or Global Positioning System (GPS)network(s) (not shown). It is to be noted that server(s) 1514 caninclude one or more processor configured to confer at least in part thefunctionality of macro network platform 1510. To that end, the one ormore processor can execute code instructions stored in memory 1530, forexample. It is should be appreciated that server(s) 1514 can include acontent manager 1515, which operates in substantially the same manner asdescribed hereinbefore. Furthermore, server(s) 1514 can embody, at leastin part, a party information component and an information interfacecomponent as disclosed elsewhere herein.

In example wireless environment 1500, memory 1530 can store informationrelated to operation of mobile network platform 1510. Information caninclude data relevant to the party information component 1517; recordsof devices (e.g., 105 ₁-105 _(J)); and so forth. Memory 1530 can alsostore information from at least one of telephony network(s) 1540, WAN1550, LAN 1570, or SS7 network 1560.

Various aspects or features described herein can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques. In particular, the aspects or featurescan be implemented through program modules stored in a memory andexecuted by a processor, and/or other combination of hardware andsoftware, e.g., firmware. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips . . . ), opticaldisks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ),smart cards, and flash memory devices (e.g., card, stick, key drive . .. ).

As used in this application, the terms “component,” “interface,”“gateway,” “connector,” and “system” (and the like) are intended torefer to a computer-related entity, either hardware, a combination ofhardware and software, software, or software in execution. For example,a component can be, but is not limited to being, a process running on aprocessor, a processor, an object, an instance, an executable, a threadof execution, a program, and/or a computer. By way of illustration, bothan application running on a computer and the computer can be acomponent. One or more components can reside within a process and/orthread of execution and a component can be localized on one computerand/or distributed between two or more computers.

Furthermore, the claimed subject matter can be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips, et cetera),optical disks (e.g., compact disk (CD), digital versatile disk (DVD), etcetera), smart cards, and flash memory devices (e.g., card, stick, keydrive, et cetera). Additionally it should be appreciated that a carrierwave can be employed to carry computer-readable electronic data such asthose used in transmitting and receiving electronic mail or in accessinga network such as the Internet or a local area network (LAN). Of course,those skilled in the art will recognize many modifications can be madeto this configuration without departing from the scope or spirit of theclaimed subject matter.

As used herein, the term “identifying information” is intended to becontact information known at the time a communication is connectedrelating to a party of the communication and can include (but is notlimited to) telephone numbers, aliases, messenger names and identifiers,e-mail addresses, extensions, device personal identification numbers(PINs), distribution lists, network addresses, component addresses(e.g., medium access control (MAC) addresses, machine addresses, etcetera) or other component identifiers, user names, nicknames, domains,signatures (electronic, physical, and otherwise), references, forwardingconfigurations, and network addresses. The term “communication” as usedwhen two or more devices correspond is intended to expansively captureall means of transmission or reception available to state-of-the-artdevices and can include (but is not limited to) cellular, satellitetransmission, VOIP and SIP voice connections, short message service(SMS) exchanges, broadcast data, network sessions, e-mails, instantmessages, other network-based messaging, PIN or other device-basedmessaging, voicemail, picture mail, video mail, mixed-contentcorrespondence, Unified Messaging (UM), and other digital and analoginformation transmitted between parties in any local and/or distant,physical and/or logical region.

Similarly, the concept of “data transmission” herein is intended tobroadly represent known means of information exchange with digital oranalog systems, including but not limited to hard-wired and directconnections (e.g., local media, universal serial bus (USB) cable,integrated drive electronics (IDE) cable, category 5 cable, coaxialcable, fiber optic cable and telephone cable), shared connections (e.g.,remote and/or distributed resources) wireless connections (e.g., Wi-Fi,Bluetooth, infrared wireless, and personal area network connections),messaging systems (e.g., short message service (SMS), instant messaging,and other network-enabled other messaging), mobile or cellulartransmissions and combinations thereof (e.g., personal communicationsystem (PCS) and integrated networks), Unified Messaging, and othermeans of techniques of communication employed by telephones, personaldigital assistants (PDAs), computers and network devices. “Mixed-contentmessage,” as used herein, is intended to represent communicationsemploying one or more means of data transmission to present one or morevarieties of device-capable content, including (but not limited to)picture messages, audio or video messages, and messages where text orother media types accompany one another. A “user device” can include,but is not limited to, data-enabled telephones (cellular telephones,smart phones, soft phones, VOIP and SIP phones, satellite phones,telephones coupled to computer systems, et cetera), communicationsreceivers, personal digital assistants, pagers, portable e-mail devices,portable web browsers, media devices capable of receiving data, portablecomputers, and other electronics that allow a user to receivecommunications from other parties.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor can also be implemented as acombination of computing processing units.

In the subject specification, terms such as “data store,” data storage,”“database,” and substantially any other information storage componentrelevant to operation and functionality of a component, refer to “memorycomponents,” or entities embodied in a “memory” or components comprisingthe memory. For example, information relevant to operation of variouscomponents described in the disclosed subject matter, and that can bestored in a memory, can comprise historic data on previously servedqueries; communication party information from various sources; files andapplications; and so forth. It is to be appreciated that the memorycomponents described herein can be either volatile memory or nonvolatilememory, or can include both volatile and nonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

What has been described above includes examples of aspects of theclaimed subject matter. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the claimed subject matter, but one of ordinary skill in theart can recognize that many further combinations and permutations of thedisclosed subject matter are possible. Accordingly, the disclosedsubject matter is intended to embrace all such alterations,modifications and variations that fall within the spirit and scope ofthe appended claims. Furthermore, to the extent that the terms“includes,” “has” or “having” are used in either the detaileddescription or the claims, such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim. Embodiments andexamples provided in the foregoing are non-exhaustive and understood tocapture similar functionality known as of the disclosures herein.

1. A system, comprising: a processor; and a memory that storesexecutable instructions that, when executed by the processor, facilitateperformance of operations, comprising: in response to party informationbeing determined to be represented in contact history information of adevice at which a call is received, facilitating a first display ofinformation from the contact history information, wherein the partyinformation is about a communication party identity associated with atelephone number from which the call is initiated, and the contacthistory information represents a history of communications of the devicewith respect to party identities associated with the device; and inresponse to the party information being determined not to be representedin the contact history information of the device, facilitating a seconddisplay of the party information received from query results retrievedfrom a publicly accessible data store.
 2. The system of claim 1, whereinthe operations further comprise: querying the publicly accessible datastore for additional information relating to the party information. 3.The system of claim 2, wherein the querying is performed without arequest for the additional information being received by the system. 4.The system of claim 1, wherein the operations further comprise: storingthe party information for reuse in another communication comprising thecommunication party identity as a party identity.
 5. The system of claim1, wherein the operations further comprise: enabling the communicationparty identity to provide input.
 6. The system of claim 5, wherein theinput enables the communication party to opt-out of query service basedupon which the second display of the party information is facilitated.7. The system of claim 1, wherein the facilitating the second displaycomprises facilitating a selection of a portion of the party informationthat is displayed.
 8. The system of claim 7, wherein the operationsfurther comprise: requesting additional information relating to theselection.
 9. The system of claim 8, wherein the operations furthercomprise: facilitating a display of the additional information relatingto the selection.
 10. The system of claim 1, wherein the facilitatingthe first display is performed during the call.
 11. The system of claim1, wherein the facilitating the second display is performed during thecall.
 12. The system of claim 1, wherein the facilitating the firstdisplay is performed after termination of the call.
 13. Acomputer-readable storage device storing computer-executableinstructions that, in response to execution, cause a system comprising aprocessor to perform operations, comprising: in response to partyinformation being determined to be represented in contact historyinformation of a device at which a call is received, facilitating afirst display of information from the contact history information,wherein the party information is about a communication party identityassociated with a telephone number from which the call originates, andthe contact history information represents a history of communicationsof the device with respect to party identities associated with thedevice; and in response to the party information being determined not tobe represented in the contact information of the device, querying a datastore that is available to the public, and facilitating a second displayof the party information received from query results retrieved from thedata store.
 14. The non-transitory computer-readable storage device ofclaim 13, wherein the party information is not stored in the contactinformation, and wherein the operations further comprise: enablingselection of a portion of the party information.
 15. The non-transitorycomputer-readable storage device of claim 14, wherein the operationsfurther comprise: requesting additional information relating to theselection.
 16. The non-transitory computer-readable storage device ofclaim 15, wherein the operations further comprise: in response toreceiving the additional information, facilitating display of theadditional information with the second display of the party information.17. A method, comprising: in response to party information beingdetermined to be represented in contact history information of a deviceat which a call is received, facilitating a first display of informationfrom the contact history information, wherein the party information isabout an identity associated with a telephone number from which the callis initiated, and the contact history information represents a historyof communications of the device with respect to party identitiesassociated with the device; and in response to the party informationbeing determined not to be represented in the contact historyinformation of the device, facilitating a second display of the partyinformation received from query results using an interface to a publicdata store.
 18. The method of claim 17, wherein the party information isnot stored in the contact history, and further comprising: enabling, bythe system, selection of a portion of the party information.
 19. Themethod of claim 18, further comprising: requesting, by the system,additional information relating to the selection.
 20. The method ofclaim 19, further comprising: facilitating, by the system, theadditional information relating to the selection being displayed withthe other display of the party information.